On Fri, 9 Sep 2022 20:13:53 -0700 (PDT), Frank Krygowski
That's what I guessed you were trying to accomplish. I have a little
ancient experience with that. A former customer deals with rating
trails for handicapped access.
<
https://www.beneficialdesigns.com/assessment/trails/>
<
https://www.beneficialdesigns.com/assessment/trails/tools/utap/>
Basically, it's a bicycle fork and wheel, loaded with sensors,
connected to a data logger, and pushed along by a cart. The sensors
record trail characteristics, which is eventually fed to a computer
program for analysis. I don't know the capabilities of the current
device, but I suspect some of the technology could be adapted to
characterize (or model) cycling roads. It would be rather interesting
and amusing to try modeling a singletrack MTB trail.
>I like the idea of using Watts and Watt-hours in some way, but of course that,
>like anything else, is complicated. Both are dependent on speed and weight.
>If an overweight and slow person did a particular ride, his power and energy
>consumption would be much different than those of a real athlete.
I can think of some additional factors that might cause problems. What
I see is that there are so many variables in characterizing a road,
that the product of the errors and variations caused by all these
variable could result is a useless and inconsistent road rating.
The real problem I have with the idea of rating roads and trails is
the lack of a useful purpose. If we had an "index of difficulty" on
various bicycle routes, how would it be used? A single number for a
given ride tells me nothing useful. It's as bad as using the sum of
the ascents to gauge difficulty, while long flat rides as zero effort.
With a single number, it would probably be possible be possible for a
short but bumpy ride, to be equally "difficult" as a long ride on a
long flat road. So, we add numbers for road characteristics, such as
surface roughness. But roads are not homogenous and vary
substantially along their length. Do we assign a different
"difficulty" number for each mile? Anyway, I like the idea, but I
don't see any way to make it useful.
>I'm just musing while watching TV. But this discussion is more interesting than
>most of the totally off-topic things posted here.
Most of what I write in RBT is off topic. When I used to dive deep
into bicycle related topics, there was usually someone who didn't like
the idea of making measurements and doing calculations, who suggested
that I should simply build and ride such a bicycle and not bother with
the engineering. That's when I realized that in RBT, a report from a
test ride is far more convincing than detailed calculations.
>- Frank Krygowski